Fix tests after framework version bump - #300
Conversation
|
Warning Review limit reached
Next review available in: 52 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe feature fixtures now expect scaffolded packages and generated README files to require WP-CLI 3.0 instead of WP-CLI 2.13. ChangesScaffold version expectations
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@features/scaffold-package.feature`:
- Around line 45-47: Restore the fixture expectations to the current scaffold
default: in features/scaffold-package.feature lines 45-47, expect ^2.13 instead
of ^3.0; in features/scaffold-package-readme.feature lines 41-44 and 81-84,
expect v2.13 instead of v3.0. Keep the scaffold implementation unchanged unless
its default is intentionally being updated.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: e2e80848-9828-4153-887d-d1d60e6ee1cc
📒 Files selected for processing (2)
features/scaffold-package-readme.featurefeatures/scaffold-package.feature
There was a problem hiding this comment.
Pull request overview
Updates Behat acceptance test expectations to reflect a WP-CLI 3.0 baseline after the framework version bump, primarily by adjusting expected scaffolded output (composer constraints and generated README wording).
Changes:
- Bumped expected scaffolded
composer.jsonWP-CLI requirement from^2.13to^3.0. - Updated expected generated README wording to state “WP-CLI v3.0 or greater”.
- Updated multiple scaffold-package-readme scenarios’ embedded composer.json expectations to
^3.0.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| features/scaffold-package.feature | Updates expected scaffolded package composer.json WP-CLI version constraint to ^3.0. |
| features/scaffold-package-readme.feature | Updates expected generated README wording and embedded composer.json requirements to WP-CLI v3.0+ / ^3.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary by CodeRabbit